home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gold Medal Software 2
/
Gold Medal Software Volume 2 (Gold Medal) (1994).iso
/
bbsutils
/
tb502man.arj
/
P116
< prev
next >
Wrap
Text File
|
1994-02-13
|
2KB
|
53 lines
The TriBBS Bulletin Board System 116
frontend event. If you are running TriBBS as a door, simply let your
main board run the necessary events.
Error Correcting Connections
----------------------------
If your frontend is able to supply an error correcting message (i.e.
ARQ, etc.), it may be specified with a slightly modified version of
TriBBS's "/F" command line switch: "/F baud rate/error correcting
message". Please note the slash between the "baud rate" and "error
correcting message" parameters. This slash is essential for TriBBS to
be able to correctly parse the "/F" command line switch.
Limiting Time
-------------
A user's log on time can be limited with TriBBS's "/T" command line
switch. The format for this command line switch is "/Tminutes".
Where "minutes" is the maximum number of minutes the caller should be
allowed for this call.
Forced Hang Up
--------------
Normally, TriBBS does not hang up on the caller when he says goodbye.
It leaves the task of hanging up to the frontend program or the main
board. If your frontend doesn't hang up before recycling, you can use
TriBBS's "/H" command line switch to instruct it to hang up on the
caller before returning to the frontend.
IMPORTANT: Whenever a caller is in a door, TriBBS creates a file
called DOORS.TMP in the node's NWORK directory. TriBBS uses this file
to determine if a caller is returning from a door when BBS.EXE is
restarted. Therefore, it is essential that your frontend's batch file
delete DOORS.TMP before running BOARD.BAT. Otherwise, if carrier is
lost in a door, BBS.EXE will assume that a caller is returning from a
door when the frontend program calls it the next time. Consequently,
the next caller will be logged on under the previous caller's account.